Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[stable22] Mention missing files subdir #32918

Merged
merged 1 commit into from
Jun 24, 2022
Merged

Conversation

backportbot-nextcloud[bot]
Copy link

@backportbot-nextcloud backportbot-nextcloud bot commented Jun 17, 2022

backport of #32874

Many users are getting confused by the inaccurate error message "Home storage for user $user not writable" because the storage *is* writable.  The actual issue is a missing files/ subdirectory.  cf. https://help.nextcloud.com/t/home-storage-for-user-not-writable/10831/7
By mentioning the possible cause in the error message, users are going to be able to rapidly solve their problem rather than bang their heads against the screen, Google, and eventually forums to find out that the error message is wrong in their case.
Yes, it would be better to detect and precisely describe the fault, or fix the problem automatically, but until then, be kind to the users for the next however many years.
@blizzz blizzz added the 4. to release Ready to be released and/or waiting for tests to finish label Jun 24, 2022
@blizzz blizzz merged commit d427ea1 into stable22 Jun 24, 2022
@blizzz blizzz deleted the backport/32874/stable22 branch June 24, 2022 08:11
@skjnldsv skjnldsv mentioned this pull request Jul 5, 2022
8 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4. to release Ready to be released and/or waiting for tests to finish enhancement feature: occ
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants